Skip to content

docs(settings): clarify horizontal vs vertical distance units#14599

Closed
Bartok9 wants to merge 1 commit into
mavlink:masterfrom
Bartok9:aerial/docs-units-vertical-2026-07-13
Closed

docs(settings): clarify horizontal vs vertical distance units#14599
Bartok9 wants to merge 1 commit into
mavlink:masterfrom
Bartok9:aerial/docs-units-vertical-2026-07-13

Conversation

@Bartok9

@Bartok9 Bartok9 commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Document that QGC tracks horizontal vs vertical distance display units separately.
  • Clarify that altitude/height facts use the vertical distance axis (vertical m in FactMetaData).
  • Align the Units list in Settings → General with Distance + Vertical Distance.

Motivation

Operators troubleshooting wrong altitude displays after changing units currently only see a single “Distance” bullet. This notes the dual-axis model and lists Vertical Distance explicitly.

Testing

  • Docs-only review of docs/en/qgc-user-guide/settings_view/general.md

Related

@github-actions

github-actions Bot commented Jul 13, 2026

Copy link
Copy Markdown
Contributor

⚠️ Build results unavailable — artifact download from one or more platform workflows failed (likely artifact retention expiry or transient API error). The combined report cannot be generated for this run.

See the Build Results workflow run for details.

@DonLakeFlyer DonLakeFlyer added this to the Release V5.1 milestone Jul 16, 2026
Document that Fact length display splits horizontal (m) and vertical
(vertical m) axes, and list Vertical Distance under Settings → General.
@Bartok9

Bartok9 commented Jul 22, 2026

Copy link
Copy Markdown
Contributor Author

Closing remaining open work — standing down all automated coding on this repo until further notice per maintainer feedback. Thanks for your time.

@Bartok9 Bartok9 closed this Jul 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants